SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 36599: Connection failures to a SAS Pooled Workspace Server may occur under heavy load.

DetailsAboutRate It

Connection failures to a SAS Pooled Workspace server may occur if a system runs out of ephemeral ports, or the range of ports used by the operating system for ephemeral ports includes the object spawner port bank.

The SAS Object Spawner log will contain the following error:

Failed to start server.

and/or ...

A port could not be obtained to allow the client to be connected to this server.

The SAS Pooled Workspace server log will contain the following error:

The TCP/IP tcpSockBind support routine failed with error 10048 (The specified address is already in use.).

On a Windows system prior to Windows Vista, the resolution is to raise the ephemeral port limit by setting the MaxUserPort value in the system registry to the max value of 65534.

How to increase the maximum number of ephemeral ports.

After setting the MaxUserPort value, the ports specified for the SAS Object Spawner port bank should be reserved so that the system does not try to use them as ephemeral ports. Default port numbers in the port bank are 8801, 8811, 8821.

How to reserve a range of ephemeral ports on a computer.

On a Linux system, edit the /etc/sysctl.conf file and add the following line:

# Allowed local port range net.ipv4.ip_local_port_range = 32768 65000

The network and SAS® servers must be restarted for the change to take effect. The following command can be used to manually restart the network:

[root] /# /etc/rc.d/init.d/network restart

In a few instances, the Linux operating system had to be rebooted before the change took effect.

All other UNIX operating systems do not need these changes.



Operating System and Release Information

Product FamilyProductSystemSAS Release
ReportedFixed*
SAS SystemN/AWindows Vista for x649.2 TS2M09.3 TS1M0
Microsoft Windows XP Professional9.2 TS2M09.3 TS1M0
Windows Vista9.2 TS2M09.3 TS1M0
Microsoft Windows Server 2008 for x649.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 for x649.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Standard Edition9.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Datacenter Edition9.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Enterprise Edition9.2 TS2M09.3 TS1M0
Microsoft® Windows® for x649.2 TS2M09.3 TS1M0
Microsoft Windows XP 64-bit Edition9.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.2 TS2M09.3 TS1M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.2 TS2M09.3 TS1M0
z/OS9.2 TS2M09.3 TS1M0
Microsoft® Windows® for 64-Bit Itanium-based Systems9.2 TS2M09.3 TS1M0
64-bit Enabled AIX9.2 TS2M09.3 TS1M0
64-bit Enabled HP-UX9.2 TS2M09.3 TS1M0
64-bit Enabled Solaris9.2 TS2M09.3 TS1M0
HP-UX9.2 TS2M09.3 TS1M0
HP-UX IPF9.2 TS2M09.3 TS1M0
Linux9.2 TS2M09.3 TS1M0
Linux for x649.2 TS2M09.3 TS1M0
Linux on Itanium9.2 TS2M09.3 TS1M0
OpenVMS on HP Integrity9.2 TS2M09.3 TS1M0
Solaris for x649.2 TS2M09.3 TS1M0
Tru64 UNIX9.2 TS2M09.3 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.